﻿<?xml version="1.0" encoding="utf-8"?>
<!--Code Generated Analysis XML-->
<ULA>
  <Configuration>
    <Version>1.0.0</Version>
    <Product>SharePoint Server</Product>
    <Analysis>
      <Category>Search</Category>
      <XMLDescription>Search</XMLDescription>
    </Analysis>
  </Configuration>
  <ULAQuery>
    <Query>
	<ID>a0c6da00-59da-4c78-a6b8-522de7d4298b</ID>
	<Title>Search crawl component index path error - Events 2588 2589 </Title>
	<Parameters>
		<EventID>Events 2588 2589 </EventID>
		<Message>http://technet.microsoft.com/en-us/library/ff453931</Message>
		<SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '2588' OR EventID = '2589'</SQLQuery>
		<RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '2588' OR EventID = '2589'</RelevantLogCollection>
		<Symptom>These events might appear in the event log:

Event ID: 2588 Description: The index location for component [data] for application [data] is invalid: [data].


Event ID: 2589 Description: The index location for component [data] for application [data] is invalid: unauthorized access to [data].
</Symptom>
		<Description>When each search crawl component is created, it creates a folder to use for storing index files that are used as part of the crawling process.
</Description>
		<Cause>The location provided for the index did not exist, or the application did not have rights to create a folder for the index at the location.
</Cause>
		<Articles>http://technet.microsoft.com/en-us/library/ff453931</Articles>
	</Parameters>
</Query>
    <Query>
      <ID>f8e39a1b-2406-4a04-9f64-9ea22f4feb7f</ID>
      <Title>Search administration component failed - Event 121 </Title>
      <Parameters>
        <EventID>121</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee924658</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '121'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '121'</RelevantLogCollection>
        <Symptom>When the search service application is being modified and the administration component fails, one or more of the following symptoms might appear:

The action of modifying the search application setting is not completed.


This event appears in the event log: Event ID: 121 Description: The administration component for application ‘[data]’ failed with exception ‘[data]’ .
</Symptom>
        <Description>A search administration component is created for each search service application. The search administration component modifies search application settings.
</Description>
        <Cause>The search administration component is not correctly configured, or it cannot connect to the search application administration database.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee924658</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>d5e33a50-f7f3-4e20-b12b-ac6d2a12b717</ID>
      <Title>Search gatherer host unavailable - Event 114 </Title>
      <Parameters>
        <EventID>114</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513100</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '114'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '114'</RelevantLogCollection>
        <Symptom>When Microsoft SharePoint Server 2010 is crawling content from a specific content server and network communication problems exist, Microsoft SharePoint Server might display the following symptoms:

The crawl of the specific content server does not progress and appears to stall.


The crawl logs show no new crawled documents for the specific content server.


This event appears in the event log: Event ID: 114 Description: The server [data] is unavailable and could not be accessed. The server is probably disconnected from the network. Items from this server will be skipped by the crawl for the next 10 minutes [data].
</Symptom>
        <Description>As part of a search crawl, the servers that contain the crawl components communicate with content servers to retrieve the items for the crawl. Network communication problems between crawl server and content server will inhibit this crawl.
</Description>
        <Cause>Network issues might be preventing the communication. Check that the content server is online and can connect to the crawl server.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513100</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>bdc71911-051b-4905-986f-64cff33ff7d4</ID>
      <Title>Search propagation communication error - Event 92 </Title>
      <Parameters>
        <EventID>92</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513077</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '92'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '92'</RelevantLogCollection>
        <Symptom>When Microsoft SharePoint Server 2010 is crawling content, and the crawl component cannot propagate to the query server, SharePoint Server 2010 displays the following symptoms:

The crawl does not progress and appears to stall.


The crawl logs show no new crawled documents.


Users might not be able to view applications in their browsers, or the service may otherwise be unavailable


This event appears in the event log: Event ID: 92 Description: A Crawl Component for search application ‘[data]’ could not communicate with the query server ‘[data]’.
</Symptom>
        <Description>As the crawler searches content to create an index, it creates index files to use for retrieving search results. These files are created by the crawl component in its storage area, and then propagated to the appropriate query components.
</Description>
        <Cause>One or more of the following might be the cause:

The crawl component might have stale, or expired, credentials. 


Network issues might prevent the communication.


The query server might be unresponsive.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513077</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>a6e14fbc-c7e9-4f3e-b824-ca9e1fa32190</ID>
      <Title>Search indexer low disk space - Event 80 </Title>
      <Parameters>
        <EventID>80</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513130</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '80'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '80'</RelevantLogCollection>
        <Symptom>Microsoft SharePoint Server 2010 displays the following symptoms while the crawler searches content:

The crawl does not progress and appears to stall.


The crawl logs show no new crawled documents.


This event appears in the event log: Event ID: 80 Description: [data] Very low disk space was detected for catalog [data]. Please free up some disk space so that crawling can continue.
</Symptom>
        <Description>As the crawler searches content to create an index, it creates index files to use for retrieving search results. As more items are indexed, the index files grow in size:
</Description>
        <Cause>One or more of the following issues might be the cause: 

If the error was reported against a crawl component, the storage location associated with the crawl component is running out of space. Remove unnecessary files and folders on that drive to gain more disk space.


The storage location associated with the index of the query component is running out of space.


If the error was reported against a query component, the search application likely has outgrown the storage capacity. In this case, move the index that is associated with the query component to a larger storage device.


If the search application index contains more than 10 million items per query component, add another query group to the application, on a new server.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513130</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>c3034398-e9fb-4e74-8b3f-ae8eee15ce38</ID>
      <Title>Search index corrupted - Events 74 93 </Title>
      <Parameters>
        <EventID>Events 74 93 </EventID>
        <Message>http://technet.microsoft.com/en-us/library/ff468695</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '74' OR EventID = '93'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '74' OR EventID = '93'</RelevantLogCollection>
        <Symptom>One or more of the following symptoms might appear:

Search activities (crawl or query) that involve the query component are stalled.


One or more of these events might appear in the event log:


Event ID: 74 Description: [data] An index corruption of type [data] was detected in catalog [data]. Stack trace is [data].
</Symptom>
        <Description>The key process that drives search crawls and queries is Mssearch.exe. This process hosts the crawl and query components for search.
</Description>
        <Cause>One or more of the following might be the cause:

Disk failures are affecting the index files.


The index is corrupt.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ff468695</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>b525aa51-9874-4b0b-aa18-bc2ca0316460</ID>
      <Title>Search indexer initialization index failed - Event 71 </Title>
      <Parameters>
        <EventID>71</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513081</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '71'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '71'</RelevantLogCollection>
        <Symptom>One or more of the following symptoms might appear:

Crawl or query search activities that involve the component stall.


The system automatically retries every minute silently. If two events are thrown within 30 minutes, action should be taken.


This event appears in the event log: Event ID: 71 Description: Content index on [data] could not be initialized. Error [data]. [data]
</Symptom>
        <Description>The key process that drives crawls and queries is mssearch.exe. This process hosts the crawl and query components for search. During search initialization, Microsoft SharePoint Foundation 2010 displays the symptoms described while initializing the mssearch.exe process or a crawl or query component.
</Description>
        <Cause>One or more of the following might be the cause:

Could not access index files on disk


Lack of available memory


Index corruption
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513081</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>cc5d52ed-6f6b-4cd4-8ee7-6b08b9f7e1b4</ID>
      <Title>Search query critical error - Event 60 </Title>
      <Parameters>
        <EventID>60</EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513123</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '60'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '60'</RelevantLogCollection>
        <Symptom>Microsoft SharePoint Server 2010 experiences the following symptoms when serving queries:

Query latency increases or queries fail.


This event appears in the event log: Event ID: 60 Description: Cannot take the last query component out of rotation. Check previous event logs to determine cause. Propagation may be necessary. [data]
</Symptom>
        <Description>In scenarios where a query component has no mirror and lacks high-availability, or all query components in a query group fail, it is possible that query results will not be served for a portion of the index.
</Description>
        <Cause>A query component has been taken out of rotation due to the reason present in the previous search event's error message.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513123</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>2b4955f6-edd1-4541-96a6-88f14cac9a70</ID>
      <Title>Search relegate query component - Event 58 </Title>
      <Parameters>
        <EventID>58 </EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513126</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '58'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '58'</RelevantLogCollection>
        <Symptom>Microsoft SharePoint Server 2010 experiences the following symptoms when serving queries:

Under high query load there may be a decrease in query throughput.


This event appears in the event log: Event ID: 58 Description: Query component [data] has been taken out of rotation due to this error: [data]. It will be retried in [data] seconds. [data]
</Symptom>
        <Description> To support high availability, we recommend that multiple query components be created in the same query group. If a query component fails, the Microsoft Search Server 2010 service (OSearch) relegates the operations of the failed component to another query component to continue to serve queries.
</Description>
        <Cause>A query component was taken out of rotation for the reason presented in the event error message.
</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513126</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>47fca118-9b2a-482e-a3dd-ba516a939a1e</ID>
      <Title>Search database out of space - Event 52 </Title>
      <Parameters>
        <EventID>52 </EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513079</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '52'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '52'</RelevantLogCollection>
        <Symptom>As more items are crawled, the size of the property and crawl database increases over time. At some point, Microsoft SharePoint Server 2010 might display the following symptoms:

The crawl does not progress and seems to stall.


The crawl logs show no new crawled documents.


This event appears in the event log: Event ID: 52 Description: The database is out of space. Source:[data] Code:[data] occurred [data] time(s) Description: [data]
</Symptom>
        <Description>Each search application depends on the following sets of databases for storing a specific type of content:

One or more search property databases store metadata about the crawled items.


One or more search crawl databases store information about when and where items were crawled.


A search administration database stores information that is specific to managing the search application.</Description>
        <Cause>One or more search databases are out of disk space.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513079</Articles>
      </Parameters>
    </Query>
    <Query>
      <ID>4d3c2d6c-f172-4424-ad2f-3a8d10356c2c</ID>
      <Title>Search gatherer disk is full - Event 23 </Title>
      <Parameters>
        <EventID>23 </EventID>
        <Message>http://technet.microsoft.com/en-us/library/ee513078</Message>
        <SQLQuery>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '23'</SQLQuery>
        <RelevantLogCollection>SELECT TOP 1 * FROM [ULAtablename] WHERE EventID = '23'</RelevantLogCollection>
        <Symptom>Microsoft SharePoint Server 2010 experiences the following symptoms when it crawls content:

The crawl does not progress and seems to stall.


The crawl logs show no new crawled documents.


This event appears in the event log: Event ID: 23 Description: The crawl has been delayed because a disk is full.
</Symptom>
        <Description>As the crawler searches content to create an index, it creates files in a temporary location. This temporary location can grow in size over time. The disk where the temporary location is located is running out of space.
</Description>
        <Cause>The disk on which the search crawler creates temporary files is running out of space.</Cause>
        <Articles>http://technet.microsoft.com/en-us/library/ee513078</Articles>
      </Parameters>
    </Query>
  </ULAQuery>
</ULA>